Follow the evidence.
Not just the transaction.
Trace cross-chain execution through verifiable evidence, explicit trust assumptions, and dependency-aware revalidation. When supporting evidence changes, ChainTrace isolates affected claims without erasing historical facts.
Two transactions existing does not prove valid execution.
Traditional blockchain explorers display separate transaction receipts on disparate chains. However, observing a source transaction and a destination transaction does not guarantee they represent a causally connected, authenticated bridge execution.
The "Look-alike" Transaction Fallacy
An application monitors an event on Ethereum and observes an execution on Polygon. Without authenticating the message GUID, payload digest, and DVN quorum attestation, the application is vulnerable to rogue replays, mismatched parameters, and spoofed bridge calls.
ChainTrace Causal Verification
ChainTrace builds a directed acyclic graph connecting verified observations: source finality proofs, cryptographic GUID matching across Endpoint contracts, payload hash invariance, and destination delivery receipts with explicit evaluation timestamps.
From source observation to destination execution.
Each step in the cross-chain lifecycle is anchored by immutable cryptographic observations, versioned verification policies, and transparent trust boundaries.
Source Chain Evidence
Captures the PacketSent event on LayerZero EndpointV2, extracts the 32-byte GUID, and verifies block confirmations exceed the finality threshold.
Message Identity Match
Evaluates cryptographic identity matching. The unique guid, sender, nonce, and payload hash must match identically between source and destination packets.
Destination Execution
Inspects the destination receipt on Polygon Amoy for successful transaction status (0x1) and emitted PacketDelivered event.
Dependency-Aware Revalidation
When upstream evidence changes (such as a source chain block reorganization or policy upgrade), ChainTrace does not blind-wipe history or mislabel transactions. It traverses descendants in the DAG and marks only dependent claims as REVALIDATION_REQUIRED while preserving independent historical facts.
Interactive Reorg Demonstration
Trigger a controlled upstream block hash mutation to see topological change propagation in real time.
Cross-Chain Trail Explorer
Query live cross-chain transactions or inspect reproducible test scenarios. All data is evaluated against versioned verification rules and backed by the ChainTrace REST API.
{\n "status": 1,\n "confirmations": 28,\n "blockNumber": 5420052\n}
Transparent Trust Model
ChainTrace avoids false claims of trustless verification. Every claim records its precise verification assumptions, observation sources, and explicit protocol boundaries.
RPC Provider Honesty
Direct JSON-RPC observations rely on honest node responses. In production profiles, multi-provider quorum and consensus headers can be configured to eliminate single-provider trust.
LayerZero DVN Quorum
Message verification assumes the protocol's configured Decentralized Verifier Network (DVN) has not colluded or violated signoff rules between source and destination endpoints.
Finality Thresholds
Claims are verified only after meeting configured confirmation thresholds (12 blocks on Sepolia). Upstream reorganizations trigger automated REVALIDATION_REQUIRED transitions.